Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf6fb51840ad4e89a442ec507941c9c4f7a194a646d9a334cc1f9823b723178

Tx prefix hash: 6f9c39e70732b0e787458ae4096dca6965d51fc606c1d7d9bc57c1dfc8cddde6
Tx public key: b1129b77e9e79367e6dc16c2fea90c0feac2cca746be86bc03ea664655eee9f5
Timestamp: 1703449989 Timestamp [UCT]: 2023-12-24 20:33:09 Age [y:d:h:m:s]: 01:331:10:19:30
Block: 920349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495717 RingCT/type: yes/0
Extra: 01b1129b77e9e79367e6dc16c2fea90c0feac2cca746be86bc03ea664655eee9f502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0578465661635dfd5bf61d7881d79805de274e8d358f8e112bd8acc6cd0f17d0 0.600000000000 1378027 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": 920359, "vin": [ { "gen": { "height": 920349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0578465661635dfd5bf61d7881d79805de274e8d358f8e112bd8acc6cd0f17d0" } } ], "extra": [ 1, 177, 18, 155, 119, 233, 231, 147, 103, 230, 220, 22, 194, 254, 169, 12, 15, 234, 194, 204, 167, 70, 190, 134, 188, 3, 234, 102, 70, 85, 238, 233, 245, 2, 17, 0, 0, 0, 6, 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