Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08282dba93b52901f6a27854f3678d9457a9a4540a262d89fa2e323a8b98dfd4

Tx prefix hash: 026a24f33f618168e5e233d5d1afcdbf66642c16a08b112b04d5b13fedbd4bfe
Tx public key: 0ec13bd337f2b1f9e44bcfeb80cc3d0ce8adcd8ca34e4ec82f858f77d5cd179c
Timestamp: 1762233695 Timestamp [UCT]: 2025-11-04 05:21:35 Age [y:d:h:m:s]: 00:024:03:59:59
Block: 1404570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17307 RingCT/type: yes/0
Extra: 010ec13bd337f2b1f9e44bcfeb80cc3d0ce8adcd8ca34e4ec82f858f77d5cd179c0211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc031697e095e6ef37cf47ecf35c0d4239e6880b0066414a4ee93c8364c7e1bc 0.600000000000 1892929 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": 1404580, "vin": [ { "gen": { "height": 1404570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc031697e095e6ef37cf47ecf35c0d4239e6880b0066414a4ee93c8364c7e1bc" } } ], "extra": [ 1, 14, 193, 59, 211, 55, 242, 177, 249, 228, 75, 207, 235, 128, 204, 61, 12, 232, 173, 205, 140, 163, 78, 78, 200, 47, 133, 143, 119, 213, 205, 23, 156, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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