Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e580ee6664040fbc2e5ed1938abdf2a73cb8beef23e06d6674c9a914be8c47b

Tx prefix hash: d3fd17c6f4e6f01db61703092b6ae2c64bb209ee3d705168c34bb5349d4ad109
Tx public key: 4a3cb79470c2195503a4052496c15d76e5a2298d5aa0097e7b78ea0d151659db
Timestamp: 1673793847 Timestamp [UCT]: 2023-01-15 14:44:07 Age [y:d:h:m:s]: 02:042:01:46:58
Block: 675340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551715 RingCT/type: yes/0
Extra: 014a3cb79470c2195503a4052496c15d76e5a2298d5aa0097e7b78ea0d151659db0211000000038b7b6602000000000000000000

1 output(s) for total of 3.550734357000 dcy

stealth address amount amount idx
00: 71e1892de4bd29554838381873a45535ca3003b07fd1ac4ec7f8ee05ceeb9063 3.550734357000 1117015 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": 675350, "vin": [ { "gen": { "height": 675340 } } ], "vout": [ { "amount": 3550734357, "target": { "key": "71e1892de4bd29554838381873a45535ca3003b07fd1ac4ec7f8ee05ceeb9063" } } ], "extra": [ 1, 74, 60, 183, 148, 112, 194, 25, 85, 3, 164, 5, 36, 150, 193, 93, 118, 229, 162, 41, 141, 90, 160, 9, 126, 123, 120, 234, 13, 21, 22, 89, 219, 2, 17, 0, 0, 0, 3, 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