Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fead58a7a69c41555b9c32e09380e8bb80b1a2deff253c953d99294955d125e9

Tx prefix hash: 04d2f90174d6f0b0178c25a5e2feb32ea06ed45eeb70ec4779228b5160fd8da1
Tx public key: 4ff838bb034dea5731a6076fa9c1e2ff9ddfeef1f10341a4047e25fdc5721b5a
Timestamp: 1763290345 Timestamp [UCT]: 2025-11-16 10:52:25 Age [y:d:h:m:s]: 00:011:20:36:52
Block: 1413328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8487 RingCT/type: yes/0
Extra: 014ff838bb034dea5731a6076fa9c1e2ff9ddfeef1f10341a4047e25fdc5721b5a02110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 193d06281c448aae43819aeae34bc303c2a981f4953d0d9ac1f3833ea8852ce9 0.600000000000 1901807 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": 1413338, "vin": [ { "gen": { "height": 1413328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "193d06281c448aae43819aeae34bc303c2a981f4953d0d9ac1f3833ea8852ce9" } } ], "extra": [ 1, 79, 248, 56, 187, 3, 77, 234, 87, 49, 166, 7, 111, 169, 193, 226, 255, 157, 223, 238, 241, 241, 3, 65, 164, 4, 126, 37, 253, 197, 114, 27, 90, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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