Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33181aea0b95ce0d015c071498432ae2dd734d512793778728b13f01de0e025a

Tx prefix hash: 974b9c6ea5bdb65719ad17ec28cfb9f8880bc97dff5aaa2cb30779f9de7fe320
Tx public key: e4d028fdb47142b1714f2fb61e78c5a64e59318fbee8093ac04adbc8b1f95521
Timestamp: 1760661693 Timestamp [UCT]: 2025-10-17 00:41:33 Age [y:d:h:m:s]: 00:081:14:43:20
Block: 1391548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58426 RingCT/type: yes/0
Extra: 01e4d028fdb47142b1714f2fb61e78c5a64e59318fbee8093ac04adbc8b1f95521021100000008df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88fe0559fc6caf3ea2225674431a62f642d8c7f1206cce00fc78c499e33c6e9 0.600000000000 1879795 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": 1391558, "vin": [ { "gen": { "height": 1391548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88fe0559fc6caf3ea2225674431a62f642d8c7f1206cce00fc78c499e33c6e9" } } ], "extra": [ 1, 228, 208, 40, 253, 180, 113, 66, 177, 113, 79, 47, 182, 30, 120, 197, 166, 78, 89, 49, 143, 190, 232, 9, 58, 192, 74, 219, 200, 177, 249, 85, 33, 2, 17, 0, 0, 0, 8, 223, 90, 36, 122, 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