Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bad9e6837896b938ed4de7f305620a354fab3fa2d05bca5c113d74362b2143eb

Tx prefix hash: 075ceea55f5c62401292545ae5ac20c0646614408e7ae55014fe0a9748aacbd4
Tx public key: fc2b8f3e3ff91087f049aed9f25ad5f58a2f717db3cf69855bb352106437a6f8
Timestamp: 1762591261 Timestamp [UCT]: 2025-11-08 08:41:01 Age [y:d:h:m:s]: 00:020:00:47:54
Block: 1407538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14343 RingCT/type: yes/0
Extra: 01fc2b8f3e3ff91087f049aed9f25ad5f58a2f717db3cf69855bb352106437a6f80211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f280c7c1859c49b507f5216bb9d58c4428828efea11e9e68b8da161f98b78d3 0.600000000000 1895959 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": 1407548, "vin": [ { "gen": { "height": 1407538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f280c7c1859c49b507f5216bb9d58c4428828efea11e9e68b8da161f98b78d3" } } ], "extra": [ 1, 252, 43, 143, 62, 63, 249, 16, 135, 240, 73, 174, 217, 242, 90, 213, 245, 138, 47, 113, 125, 179, 207, 105, 133, 91, 179, 82, 16, 100, 55, 166, 248, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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