Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e17dd7d7f31d1142e9d282becd488561ada6cabb079690446b4c668e201858

Tx prefix hash: 3ddaa24b719edf1e93085524bce15fbeb217e28b4dc7fd7e219d07da9f2cbbcc
Tx public key: a94c9b053eacd0dfc4bc18f9bb0bc3d460d1037e6a807f15ac67aeb855001080
Timestamp: 1743137684 Timestamp [UCT]: 2025-03-28 04:54:44 Age [y:d:h:m:s]: 00:255:07:02:27
Block: 1248890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180218 RingCT/type: yes/0
Extra: 01a94c9b053eacd0dfc4bc18f9bb0bc3d460d1037e6a807f15ac67aeb855001080021100000006d2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4404a8b9584d9a09a09ca51e8a15474faf84721367d02729dca1e0f068183665 0.600000000000 1735925 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": 1248900, "vin": [ { "gen": { "height": 1248890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4404a8b9584d9a09a09ca51e8a15474faf84721367d02729dca1e0f068183665" } } ], "extra": [ 1, 169, 76, 155, 5, 62, 172, 208, 223, 196, 188, 24, 249, 187, 11, 195, 212, 96, 209, 3, 126, 106, 128, 127, 21, 172, 103, 174, 184, 85, 0, 16, 128, 2, 17, 0, 0, 0, 6, 210, 228, 14, 253, 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