Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26043e8cc2639c94a023bb4bfa2b725448a7f31ec45170cdec19dbe30ba1fce0

Tx prefix hash: b13d211690e6f5a3c6f6baa34f5384efc6d3dd6643d59d22b0ad9992e693e360
Tx public key: 3a029f1b3f29120c8ab4ea75670c1a1efbab80e6852e6921f4e9a26b2c55d628
Timestamp: 1766247039 Timestamp [UCT]: 2025-12-20 16:10:39 Age [y:d:h:m:s]: 00:001:18:34:45
Block: 1437832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1265 RingCT/type: yes/0
Extra: 013a029f1b3f29120c8ab4ea75670c1a1efbab80e6852e6921f4e9a26b2c55d6280211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea8e900985f1c11bf89bb0e4a7d8bea3246edbbd0b4a83166f5fdd9a2e1c56df 0.600000000000 1926643 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": 1437842, "vin": [ { "gen": { "height": 1437832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea8e900985f1c11bf89bb0e4a7d8bea3246edbbd0b4a83166f5fdd9a2e1c56df" } } ], "extra": [ 1, 58, 2, 159, 27, 63, 41, 18, 12, 138, 180, 234, 117, 103, 12, 26, 30, 251, 171, 128, 230, 133, 46, 105, 33, 244, 233, 162, 107, 44, 85, 214, 40, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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