Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27de5abca4fa7b1038fa1db9fd8218332d32a3cab942f2ec3e36388f5fa7ebf8

Tx prefix hash: cd2ff90b4295a80ba9f0912bf3f67ff33074144a4f52878400654b0a598390e6
Tx public key: 74e688396bbdcd2a4b9a8ca3664bd5e8de0b0f124cc20e14a85324d87b4564b8
Timestamp: 1741964937 Timestamp [UCT]: 2025-03-14 15:08:57 Age [y:d:h:m:s]: 00:290:07:12:28
Block: 1239201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205253 RingCT/type: yes/0
Extra: 0174e688396bbdcd2a4b9a8ca3664bd5e8de0b0f124cc20e14a85324d87b4564b802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b65ede8709713a27bf12f3fb0d55d76aca75b9b3cf0ef20a4037bcac266fe0 0.600000000000 1726166 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": 1239211, "vin": [ { "gen": { "height": 1239201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b65ede8709713a27bf12f3fb0d55d76aca75b9b3cf0ef20a4037bcac266fe0" } } ], "extra": [ 1, 116, 230, 136, 57, 107, 189, 205, 42, 75, 154, 140, 163, 102, 75, 213, 232, 222, 11, 15, 18, 76, 194, 14, 20, 168, 83, 36, 216, 123, 69, 100, 184, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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