Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 951fe3515f5cb254f74569ed2021c01f699533d124431c6462d5fe8f3e9de1b2

Tx prefix hash: 15af9e967b0e6ce188221d4fc9402171ed34772fff0a993cad0ca280d6c449fc
Tx public key: 668ac497c38c1b7a5e88c716f1c2f1ac0efb6d212479a1a5da6af30643d25671
Timestamp: 1714129867 Timestamp [UCT]: 2024-04-26 11:11:07 Age [y:d:h:m:s]: 01:029:12:18:31
Block: 1008890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282059 RingCT/type: yes/0
Extra: 01668ac497c38c1b7a5e88c716f1c2f1ac0efb6d212479a1a5da6af30643d2567102110000000318ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac8cd4105f77ef92f556f00cdce117a03e938004693b78677c4fdf32eeb95e7f 0.600000000000 1470390 of 15

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": 1008900, "vin": [ { "gen": { "height": 1008890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac8cd4105f77ef92f556f00cdce117a03e938004693b78677c4fdf32eeb95e7f" } } ], "extra": [ 1, 102, 138, 196, 151, 195, 140, 27, 122, 94, 136, 199, 22, 241, 194, 241, 172, 14, 251, 109, 33, 36, 121, 161, 165, 218, 106, 243, 6, 67, 210, 86, 113, 2, 17, 0, 0, 0, 3, 24, 236, 144, 96, 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