Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f851732be9f40c1cab7c5fc62d9ef93603ab7f5994639b6d94820797dcf08d30

Tx prefix hash: ef7cc78e0f3f0d905abd25de85feed9fddd301388a63d9b8f4e5186b44d44fe9
Tx public key: f65a126949d3299b1187afc335bbff3adb1d4d73ce30b0e935a4cdc2e5b2d186
Timestamp: 1673928327 Timestamp [UCT]: 2023-01-17 04:05:27 Age [y:d:h:m:s]: 01:302:22:13:33
Block: 676459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477469 RingCT/type: yes/0
Extra: 01f65a126949d3299b1187afc335bbff3adb1d4d73ce30b0e935a4cdc2e5b2d1860211000000018b7b6602000000000000000000

1 output(s) for total of 3.520549616000 dcy

stealth address amount amount idx
00: c87258dab93f43b04ae430e57009e3eec043f80c278ddcb4fcb704c583f34485 3.520549616000 1118176 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 676469, "vin": [ { "gen": { "height": 676459 } } ], "vout": [ { "amount": 3520549616, "target": { "key": "c87258dab93f43b04ae430e57009e3eec043f80c278ddcb4fcb704c583f34485" } } ], "extra": [ 1, 246, 90, 18, 105, 73, 211, 41, 155, 17, 135, 175, 195, 53, 187, 255, 58, 219, 29, 77, 115, 206, 48, 176, 233, 53, 164, 205, 194, 229, 178, 209, 134, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8