Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eecf725cc921eb64b5598e9ec86017451d0e4ed10a0d01212481b0b11a79ba2

Tx prefix hash: 486c0c2ee006a0771e5e82cf98b49b63c59e4d85a0be235ed41f5d91e5506bb8
Tx public key: efc05cf01cbf9f90f745193b865fa3d08a0e05e5b9913246c3febcbe525cd11c
Timestamp: 1742761023 Timestamp [UCT]: 2025-03-23 20:17:03 Age [y:d:h:m:s]: 00:243:03:05:54
Block: 1245775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171498 RingCT/type: yes/0
Extra: 01efc05cf01cbf9f90f745193b865fa3d08a0e05e5b9913246c3febcbe525cd11c021100000002c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d738f3678bb6d806d18ee1cb556cc5e9310282ed1a024aa62d7ba4104f39bc3 0.600000000000 1732766 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": 1245785, "vin": [ { "gen": { "height": 1245775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d738f3678bb6d806d18ee1cb556cc5e9310282ed1a024aa62d7ba4104f39bc3" } } ], "extra": [ 1, 239, 192, 92, 240, 28, 191, 159, 144, 247, 69, 25, 59, 134, 95, 163, 208, 138, 14, 5, 229, 185, 145, 50, 70, 195, 254, 188, 190, 82, 92, 209, 28, 2, 17, 0, 0, 0, 2, 198, 116, 9, 88, 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