Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d618252e661e35aa51efecc50ab4924f0ff9b8a800d2de762be29ae70eeaefa

Tx prefix hash: cf83b7e29feefe0b94eab1974cecfb4156b0b7031f1b8a710be14a0055cfbba4
Tx public key: a14f7a849943066febf5e7825d1a2c0623e1953f8d8216ee0ac785d85b884c2d
Timestamp: 1755460001 Timestamp [UCT]: 2025-08-17 19:46:41 Age [y:d:h:m:s]: 00:088:17:54:10
Block: 1348714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63264 RingCT/type: yes/0
Extra: 01a14f7a849943066febf5e7825d1a2c0623e1953f8d8216ee0ac785d85b884c2d02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfb13c1d90f67ab36a3fa5e821a5eb5fd16caae006b52dc049892a993a5fe112 0.600000000000 1836643 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": 1348724, "vin": [ { "gen": { "height": 1348714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfb13c1d90f67ab36a3fa5e821a5eb5fd16caae006b52dc049892a993a5fe112" } } ], "extra": [ 1, 161, 79, 122, 132, 153, 67, 6, 111, 235, 245, 231, 130, 93, 26, 44, 6, 35, 225, 149, 63, 141, 130, 22, 238, 10, 199, 133, 216, 91, 136, 76, 45, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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