Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2575a93e6add341d0d28dbb843735da1a138c2e57585c964948ce66ee578296f

Tx prefix hash: 397496d7e2a7252e36fcb6d2576196b26e0f1c8e96896b6bda20257cbaac3370
Tx public key: b57ba7de61acb0f8655c18d7ad68f7797dda381043c7954ee7776dc5145a7ff1
Timestamp: 1711322188 Timestamp [UCT]: 2024-03-24 23:16:28 Age [y:d:h:m:s]: 01:253:11:40:52
Block: 985632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439876 RingCT/type: yes/0
Extra: 01b57ba7de61acb0f8655c18d7ad68f7797dda381043c7954ee7776dc5145a7ff10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 162f2bf28713b28a744e6d3ac263d249e70bb81f76912d8a8f9f76583e8e186a 0.600000000000 1445849 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": 985642, "vin": [ { "gen": { "height": 985632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "162f2bf28713b28a744e6d3ac263d249e70bb81f76912d8a8f9f76583e8e186a" } } ], "extra": [ 1, 181, 123, 167, 222, 97, 172, 176, 248, 101, 92, 24, 215, 173, 104, 247, 121, 125, 218, 56, 16, 67, 199, 149, 78, 231, 119, 109, 197, 20, 90, 127, 241, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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