Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0234a0b1ed2ad6c50a73d54ec59027b8c560447b53751dbc41f831579cc0f65

Tx prefix hash: 23d7089b60f41c11a75fd72b4f74d7eaad91c0f23865eed7a4745f15f96a73b2
Tx public key: 99dc11c690fe9ba5f771b4a56f732c19d56e715e03bd139fbe23e50e75cb4209
Timestamp: 1738242592 Timestamp [UCT]: 2025-01-30 13:09:52 Age [y:d:h:m:s]: 00:042:23:24:10
Block: 1208373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30759 RingCT/type: yes/0
Extra: 0199dc11c690fe9ba5f771b4a56f732c19d56e715e03bd139fbe23e50e75cb4209021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 637fac47f269a64f049d120d53e17e504dcf11c9653c009b9623fe89219e21c9 0.600000000000 1695104 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": 1208383, "vin": [ { "gen": { "height": 1208373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "637fac47f269a64f049d120d53e17e504dcf11c9653c009b9623fe89219e21c9" } } ], "extra": [ 1, 153, 220, 17, 198, 144, 254, 155, 165, 247, 113, 180, 165, 111, 115, 44, 25, 213, 110, 113, 94, 3, 189, 19, 159, 190, 35, 229, 14, 117, 203, 66, 9, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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