Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0239c7e60f497c5609ee2763b271c0ed17d28bd748f5db38964fdab749a84a25

Tx prefix hash: 541b5b074c470b27b3f48067ad67c2a5c2bbc32a8440f65594230a2a171bb6ce
Tx public key: e982d51da7a97715fa2d999416c6695a4934a6b4f8c40f4f09a060c12b70dcdf
Timestamp: 1724762981 Timestamp [UCT]: 2024-08-27 12:49:41 Age [y:d:h:m:s]: 01:084:13:01:32
Block: 1097044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318881 RingCT/type: yes/0
Extra: 01e982d51da7a97715fa2d999416c6695a4934a6b4f8c40f4f09a060c12b70dcdf02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899e70d56e172dba21503ef111c1dde01613d7ae02faa61f1ca3dbfae0ff6672 0.600000000000 1572319 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": 1097054, "vin": [ { "gen": { "height": 1097044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899e70d56e172dba21503ef111c1dde01613d7ae02faa61f1ca3dbfae0ff6672" } } ], "extra": [ 1, 233, 130, 213, 29, 167, 169, 119, 21, 250, 45, 153, 148, 22, 198, 105, 90, 73, 52, 166, 180, 248, 196, 15, 79, 9, 160, 96, 193, 43, 112, 220, 223, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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