Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9f544af9d8a36fcf1d8205fa8d2320d3b957a0b6c4bdfa50f317ea07bb8c91a

Tx prefix hash: 7b154868742ab63f7c445a4dd4ba3bc0f17ff9b8c4601848f26ad6c28f351144
Tx public key: fb2468660d479b864cb0047e849c815f839cc60599c5635f95cc1a7ec9f5b16f
Timestamp: 1635337509 Timestamp [UCT]: 2021-10-27 12:25:09 Age [y:d:h:m:s]: 03:138:18:52:06
Block: 361544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877416 RingCT/type: yes/0
Extra: 01fb2468660d479b864cb0047e849c815f839cc60599c5635f95cc1a7ec9f5b16f0211000000164a0f5013000000000000000000

1 output(s) for total of 38.910796300000 dcy

stealth address amount amount idx
00: c5a39bbf1b390c9d427df3591b57ae0962c8c4bdd645b1e1cb73df9465e28dfd 38.910796300000 735516 of 0

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": 361554, "vin": [ { "gen": { "height": 361544 } } ], "vout": [ { "amount": 38910796300, "target": { "key": "c5a39bbf1b390c9d427df3591b57ae0962c8c4bdd645b1e1cb73df9465e28dfd" } } ], "extra": [ 1, 251, 36, 104, 102, 13, 71, 155, 134, 76, 176, 4, 126, 132, 156, 129, 95, 131, 156, 198, 5, 153, 197, 99, 95, 149, 204, 26, 126, 201, 245, 177, 111, 2, 17, 0, 0, 0, 22, 74, 15, 80, 19, 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