Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d07e4fdd227a585682c3dc1d7444402a5e73375f98aae46bf67630c97299d176

Tx prefix hash: 8c955b80792cae21c0db7ac7f58005738167c3b1c3d192b47fb18663f483cdf2
Tx public key: 86f2a7e8e3ea1a25e9d4d1679d7a98ac7531583ffa3685c3dda50d9be368a1c6
Timestamp: 1581301455 Timestamp [UCT]: 2020-02-10 02:24:15 Age [y:d:h:m:s]: 05:000:10:25:45
Block: 61740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153061 RingCT/type: yes/0
Extra: 0186f2a7e8e3ea1a25e9d4d1679d7a98ac7531583ffa3685c3dda50d9be368a1c602110000001c8a2ee0d9000000000000000000

1 output(s) for total of 383.204469910000 dcy

stealth address amount amount idx
00: 3c161b9330f2b105ba04e96583101ecc9c919ac91d9468d20eca9db4dacae697 383.204469910000 113847 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": 61750, "vin": [ { "gen": { "height": 61740 } } ], "vout": [ { "amount": 383204469910, "target": { "key": "3c161b9330f2b105ba04e96583101ecc9c919ac91d9468d20eca9db4dacae697" } } ], "extra": [ 1, 134, 242, 167, 232, 227, 234, 26, 37, 233, 212, 209, 103, 157, 122, 152, 172, 117, 49, 88, 63, 250, 54, 133, 195, 221, 165, 13, 155, 227, 104, 161, 198, 2, 17, 0, 0, 0, 28, 138, 46, 224, 217, 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