Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d61764cba1832553965a011034211cde7c4a4018e12b3464c039420fc6178a0

Tx prefix hash: ccb20adfe8de231ce123ca6de9c36abf41b10bc17d55c46e9c56b05436c4d906
Tx public key: c05aaef7b23b160ab4919c0c9e1a025e66ca1f0f2c47221f1075e230eb81fc36
Timestamp: 1725580074 Timestamp [UCT]: 2024-09-05 23:47:54 Age [y:d:h:m:s]: 00:126:23:01:04
Block: 1103819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90793 RingCT/type: yes/0
Extra: 01c05aaef7b23b160ab4919c0c9e1a025e66ca1f0f2c47221f1075e230eb81fc3602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddfae2c6527447db027fe419250f4b8567df59cd65af2bbcbf2001e41dcb0cfb 0.600000000000 1580796 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": 1103829, "vin": [ { "gen": { "height": 1103819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddfae2c6527447db027fe419250f4b8567df59cd65af2bbcbf2001e41dcb0cfb" } } ], "extra": [ 1, 192, 90, 174, 247, 178, 59, 22, 10, 180, 145, 156, 12, 158, 26, 2, 94, 102, 202, 31, 15, 44, 71, 34, 31, 16, 117, 226, 48, 235, 129, 252, 54, 2, 17, 0, 0, 0, 6, 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