Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e8b924009673f7ed61e4d3d1747721b6e94d37f2ab2ee694a658c86b3db5c1b

Tx prefix hash: 69efd66e2d42625753f1e161b858d4d5c52150ed18c94144e4aa5948f005905b
Tx public key: 96ca3a4180743ff2e346c5f82a3fbfe18baf32c5afc4320174ce16743a47e989
Timestamp: 1744677108 Timestamp [UCT]: 2025-04-15 00:31:48 Age [y:d:h:m:s]: 00:219:22:46:24
Block: 1261630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154926 RingCT/type: yes/0
Extra: 0196ca3a4180743ff2e346c5f82a3fbfe18baf32c5afc4320174ce16743a47e989021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a94c49def3f93adf7710861b18fc9f3479ff969f0b3764f46479370d3aefe602 0.600000000000 1748803 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": 1261640, "vin": [ { "gen": { "height": 1261630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a94c49def3f93adf7710861b18fc9f3479ff969f0b3764f46479370d3aefe602" } } ], "extra": [ 1, 150, 202, 58, 65, 128, 116, 63, 242, 227, 70, 197, 248, 42, 63, 191, 225, 139, 175, 50, 197, 175, 196, 50, 1, 116, 206, 22, 116, 58, 71, 233, 137, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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