Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87c8d2833ea5bb84565ec5b2de15b151034cf67705f8fe0eb7a46eb455853077

Tx prefix hash: df954439d71de239b40f51febce03a601ec92769da2be61edac3f2be7e8a18c0
Tx public key: 8022b663bd250d845205d20cc4b6875e3b2c5759a3e83f5c31f3f8827703a69c
Timestamp: 1763222405 Timestamp [UCT]: 2025-11-15 16:00:05 Age [y:d:h:m:s]: 00:012:01:28:21
Block: 1412759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8652 RingCT/type: yes/0
Extra: 018022b663bd250d845205d20cc4b6875e3b2c5759a3e83f5c31f3f8827703a69c0211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18675e6859c3824d6a40fc73f4e035243e7ef4bcf97e0066fd316f9aad2dbbd4 0.600000000000 1901232 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": 1412769, "vin": [ { "gen": { "height": 1412759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18675e6859c3824d6a40fc73f4e035243e7ef4bcf97e0066fd316f9aad2dbbd4" } } ], "extra": [ 1, 128, 34, 182, 99, 189, 37, 13, 132, 82, 5, 210, 12, 196, 182, 135, 94, 59, 44, 87, 89, 163, 232, 63, 92, 49, 243, 248, 130, 119, 3, 166, 156, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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