Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 219569fa67357d293e5ffef539384ff2f8a0d2ff9b427538fd63a19534c7a5fa

Tx prefix hash: 995dd160219525160249b6cb21b85055980b54dc1abb7b7f1e375597c7a13367
Tx public key: 390c82a352edd2d2ff7dc6c2a74664d159735b8c4ca8b624670b3838e4fbf983
Timestamp: 1748399591 Timestamp [UCT]: 2025-05-28 02:33:11 Age [y:d:h:m:s]: 00:169:21:25:04
Block: 1292462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119116 RingCT/type: yes/0
Extra: 01390c82a352edd2d2ff7dc6c2a74664d159735b8c4ca8b624670b3838e4fbf983021100000001523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e08c7c7799b91bcafb9ea1cbe5028fa6e07329390fa29b7b1a563e4b8d2ee381 0.600000000000 1779933 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": 1292472, "vin": [ { "gen": { "height": 1292462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e08c7c7799b91bcafb9ea1cbe5028fa6e07329390fa29b7b1a563e4b8d2ee381" } } ], "extra": [ 1, 57, 12, 130, 163, 82, 237, 210, 210, 255, 125, 198, 194, 167, 70, 100, 209, 89, 115, 91, 140, 76, 168, 182, 36, 103, 11, 56, 56, 228, 251, 249, 131, 2, 17, 0, 0, 0, 1, 82, 53, 96, 218, 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