Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 908ec916f1f021fa046af0a6e34e9d277b62d961d788dd74cc55dbbae8da40f6

Tx prefix hash: 52eb5c17fdf2ae1133dfe1c66c3fe9fd73a4aeb867cb53d1e236a4b000a01b83
Tx public key: 44ea08e84338c3d187afec967e93a51765d3e7ebd42169110762fca2483f18ec
Timestamp: 1639487958 Timestamp [UCT]: 2021-12-14 13:19:18 Age [y:d:h:m:s]: 03:090:22:52:17
Block: 395355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 843766 RingCT/type: yes/0
Extra: 0144ea08e84338c3d187afec967e93a51765d3e7ebd42169110762fca2483f18ec021100000003eaa12622000000000000000000

1 output(s) for total of 30.062502066000 dcy

stealth address amount amount idx
00: 1623b646cdde4ed699bdb046cdcdb676ce6f2597a92a32fbe93d0c455a69f704 30.062502066000 793248 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": 395365, "vin": [ { "gen": { "height": 395355 } } ], "vout": [ { "amount": 30062502066, "target": { "key": "1623b646cdde4ed699bdb046cdcdb676ce6f2597a92a32fbe93d0c455a69f704" } } ], "extra": [ 1, 68, 234, 8, 232, 67, 56, 195, 209, 135, 175, 236, 150, 126, 147, 165, 23, 101, 211, 231, 235, 212, 33, 105, 17, 7, 98, 252, 162, 72, 63, 24, 236, 2, 17, 0, 0, 0, 3, 234, 161, 38, 34, 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