Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1e4fc718656ffdcfe71ff3559f25a5f58a94ca6234d7b0e3277c843b0a74ae

Tx prefix hash: df62d2464d0694ccd78b948bbadaaf3ad0b0e81aa33169f371bf2fa72a474d82
Tx public key: 5a675e6cd7e61a4f6e16f7d89bf3b88ee6f803d2aa32b1679ccde71d312a08b9
Timestamp: 1584505029 Timestamp [UCT]: 2020-03-18 04:17:09 Age [y:d:h:m:s]: 05:205:16:18:33
Block: 84418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1301265 RingCT/type: yes/0
Extra: 015a675e6cd7e61a4f6e16f7d89bf3b88ee6f803d2aa32b1679ccde71d312a08b90211000000028c5f723a000000000000000000

1 output(s) for total of 322.349885706000 dcy

stealth address amount amount idx
00: 1303ca34a0315e239d1b431f44a09520237149da2c5a24bf19016fab19796b40 322.349885706000 153062 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": 84428, "vin": [ { "gen": { "height": 84418 } } ], "vout": [ { "amount": 322349885706, "target": { "key": "1303ca34a0315e239d1b431f44a09520237149da2c5a24bf19016fab19796b40" } } ], "extra": [ 1, 90, 103, 94, 108, 215, 230, 26, 79, 110, 22, 247, 216, 155, 243, 184, 142, 230, 248, 3, 210, 170, 50, 177, 103, 156, 205, 231, 29, 49, 42, 8, 185, 2, 17, 0, 0, 0, 2, 140, 95, 114, 58, 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