Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce74731247a02f0066c7e3e20a6dc689ebba81d20f1f2eed300f6c705ef58ab5

Tx prefix hash: 0bb95555c48dca330e79b39f946829cd867ae58335b40fd536da156c3d219dbf
Tx public key: a3e6543d458a4225206cadeea88c1655f4e85d348d5d935ce0b90f468d1df5c6
Timestamp: 1703907038 Timestamp [UCT]: 2023-12-30 03:30:38 Age [y:d:h:m:s]: 01:155:20:48:56
Block: 924124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372561 RingCT/type: yes/0
Extra: 01a3e6543d458a4225206cadeea88c1655f4e85d348d5d935ce0b90f468d1df5c602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a9e6b2f3fa68763bc1af58dce56e544fa630ae2cd393085110b08db7d740f8 0.600000000000 1381868 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": 924134, "vin": [ { "gen": { "height": 924124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a9e6b2f3fa68763bc1af58dce56e544fa630ae2cd393085110b08db7d740f8" } } ], "extra": [ 1, 163, 230, 84, 61, 69, 138, 66, 37, 32, 108, 173, 238, 168, 140, 22, 85, 244, 232, 93, 52, 141, 93, 147, 92, 224, 185, 15, 70, 141, 29, 245, 198, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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