Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58013fb647ced419e1bb0aa530bba47fe833a2348aa530ff91a472236c2e7066

Tx prefix hash: aea928f76320dc1b5319da16f6a190d52096578de9fc444a19cc59beec62fb04
Tx public key: 8db54f415f254c1d7386b8778b0854eca4a0bece5e3aae7c5e9fe89cbd38e9e5
Timestamp: 1656082739 Timestamp [UCT]: 2022-06-24 14:58:59 Age [y:d:h:m:s]: 02:266:21:23:44
Block: 529427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 711839 RingCT/type: yes/0
Extra: 018db54f415f254c1d7386b8778b0854eca4a0bece5e3aae7c5e9fe89cbd38e9e5021100000004faf35c9c000000000000000000

1 output(s) for total of 10.809080116000 dcy

stealth address amount amount idx
00: 3291cdde17cd74a7c3178f06c3b0e61b6aa6a9d00c844cf6880668a7a0cfda30 10.809080116000 958366 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": 529437, "vin": [ { "gen": { "height": 529427 } } ], "vout": [ { "amount": 10809080116, "target": { "key": "3291cdde17cd74a7c3178f06c3b0e61b6aa6a9d00c844cf6880668a7a0cfda30" } } ], "extra": [ 1, 141, 181, 79, 65, 95, 37, 76, 29, 115, 134, 184, 119, 139, 8, 84, 236, 164, 160, 190, 206, 94, 58, 174, 124, 94, 159, 232, 156, 189, 56, 233, 229, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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