Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7130956e74e85b0d870966cef75e5dbf0d91d50a5340e1224556afb404df9460

Tx prefix hash: de55ffac7a7ee210ea8f76df5a66a484bd33af5d40f276f27a7ab50f663ae13e
Tx public key: 3da3d53dc58a3945768754e512fbe042a8149076472069ba6b736d1fa933426a
Timestamp: 1737726064 Timestamp [UCT]: 2025-01-24 13:41:04 Age [y:d:h:m:s]: 00:144:06:12:49
Block: 1204322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102840 RingCT/type: yes/0
Extra: 013da3d53dc58a3945768754e512fbe042a8149076472069ba6b736d1fa933426a02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a532023e6f7d5bbc67b60b7dc02a79176dc59aa2d9d50a9940f464d90d2d8b0a 0.600000000000 1691007 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": 1204332, "vin": [ { "gen": { "height": 1204322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a532023e6f7d5bbc67b60b7dc02a79176dc59aa2d9d50a9940f464d90d2d8b0a" } } ], "extra": [ 1, 61, 163, 213, 61, 197, 138, 57, 69, 118, 135, 84, 229, 18, 251, 224, 66, 168, 20, 144, 118, 71, 32, 105, 186, 107, 115, 109, 31, 169, 51, 66, 106, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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