Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de48700058c70f1582909b06e5c6b565e7a724f516ddf46c8ac41ec9f4be51b0

Tx prefix hash: c500b4b55c99046d276b5d70ae47394f948b53d9dc2470c4735af279ae7473a3
Tx public key: 2c15f9d7a613af1c80c5e20343a72085261810d78acb0c518186e437e3422a77
Timestamp: 1717159250 Timestamp [UCT]: 2024-05-31 12:40:50 Age [y:d:h:m:s]: 00:308:21:19:01
Block: 1034008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220755 RingCT/type: yes/0
Extra: 012c15f9d7a613af1c80c5e20343a72085261810d78acb0c518186e437e3422a77021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61b924cf14827bdf93b706fb408c507964b28e14ebfd66e3066c7ee3cc3f7eb1 0.600000000000 1502481 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": 1034018, "vin": [ { "gen": { "height": 1034008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61b924cf14827bdf93b706fb408c507964b28e14ebfd66e3066c7ee3cc3f7eb1" } } ], "extra": [ 1, 44, 21, 249, 215, 166, 19, 175, 28, 128, 197, 226, 3, 67, 167, 32, 133, 38, 24, 16, 215, 138, 203, 12, 81, 129, 134, 228, 55, 227, 66, 42, 119, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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