Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37617689f58c9ea0226daab2dfb24573d5c10972e484588ce5f3c9341eefdc7f

Tx prefix hash: 0e31c44bd6b435254055fea7b7d0b03e15d67526c0fbeb2352ddee805e53289d
Tx public key: d204d1d275f75b823ebfef9bbb9ac5e48d8e1a3d9dcc9661cb615c90d8677114
Timestamp: 1728814669 Timestamp [UCT]: 2024-10-13 10:17:49 Age [y:d:h:m:s]: 01:025:21:39:51
Block: 1130639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276876 RingCT/type: yes/0
Extra: 01d204d1d275f75b823ebfef9bbb9ac5e48d8e1a3d9dcc9661cb615c90d8677114021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 842c710a245fd914d0c7c0596103962c3b43f69259fc0aeb85133ad162078fcc 0.600000000000 1613516 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": 1130649, "vin": [ { "gen": { "height": 1130639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "842c710a245fd914d0c7c0596103962c3b43f69259fc0aeb85133ad162078fcc" } } ], "extra": [ 1, 210, 4, 209, 210, 117, 247, 91, 130, 62, 191, 239, 155, 187, 154, 197, 228, 141, 142, 26, 61, 157, 204, 150, 97, 203, 97, 92, 144, 216, 103, 113, 20, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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