Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b82e546c2da95a41e5973ff7560400e1953cf78cf10c92ebd0b6e98a3df8776

Tx prefix hash: 392f385eab5b94663f8f4a37532f691222249926c71a971b6249f5d3e340a11e
Tx public key: a7631dcd3987bf38d3dcab89a809b7841d73e9b7325afeeb134916f4ed1dce31
Timestamp: 1715243798 Timestamp [UCT]: 2024-05-09 08:36:38 Age [y:d:h:m:s]: 01:182:21:31:15
Block: 1018129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389326 RingCT/type: yes/0
Extra: 01a7631dcd3987bf38d3dcab89a809b7841d73e9b7325afeeb134916f4ed1dce3102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9267754a28a7fddf6fd3013092d3dcab59878f369e1091a3a6480721c0ed6ad 0.600000000000 1481916 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": 1018139, "vin": [ { "gen": { "height": 1018129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9267754a28a7fddf6fd3013092d3dcab59878f369e1091a3a6480721c0ed6ad" } } ], "extra": [ 1, 167, 99, 29, 205, 57, 135, 191, 56, 211, 220, 171, 137, 168, 9, 183, 132, 29, 115, 233, 183, 50, 90, 254, 235, 19, 73, 22, 244, 237, 29, 206, 49, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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