Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 802a90b0c92c98f68f62312132275d32af6b4390c218c7499175f803142bc881

Tx prefix hash: 10c1351359c3630fa57986e1e7a0d0f92d48e1da523d6683659010a31ddf2517
Tx public key: f52a1ac549b2460a73c7b0315d5c1ef56f4c2c4a1979124f8bebc17aa7d9351a
Timestamp: 1729013810 Timestamp [UCT]: 2024-10-15 17:36:50 Age [y:d:h:m:s]: 01:024:18:51:04
Block: 1132283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276083 RingCT/type: yes/0
Extra: 01f52a1ac549b2460a73c7b0315d5c1ef56f4c2c4a1979124f8bebc17aa7d9351a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 450328928bc08d21f1f81042c653c6c735d4a4c72ba5700a22bcccb24a564726 0.600000000000 1615196 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": 1132293, "vin": [ { "gen": { "height": 1132283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "450328928bc08d21f1f81042c653c6c735d4a4c72ba5700a22bcccb24a564726" } } ], "extra": [ 1, 245, 42, 26, 197, 73, 178, 70, 10, 115, 199, 176, 49, 93, 92, 30, 245, 111, 76, 44, 74, 25, 121, 18, 79, 139, 235, 193, 122, 167, 217, 53, 26, 2, 17, 0, 0, 0, 3, 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