Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87348c0092a96693c1fa0234ed014d09119c53490c3a1b52398c23f2f2185744

Tx prefix hash: 85629f1d201357970225de323b2cf3f4265dce362dcd21e927f54148d0dd9362
Tx public key: 0e9f483eddfad4c4bfc6b963aae7270db8c17c710c8680f80669a51f7ad1af55
Timestamp: 1647616478 Timestamp [UCT]: 2022-03-18 15:14:38 Age [y:d:h:m:s]: 02:280:20:51:14
Block: 461180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720277 RingCT/type: yes/0
Extra: 010e9f483eddfad4c4bfc6b963aae7270db8c17c710c8680f80669a51f7ad1af55021100000002bf7ee4e7000000000000000000

1 output(s) for total of 18.193634992000 dcy

stealth address amount amount idx
00: f0a1e92df79ac4accab7c34013c52c7539392ed995fa7a0f735d1263a63d6878 18.193634992000 878361 of 0

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": 461190, "vin": [ { "gen": { "height": 461180 } } ], "vout": [ { "amount": 18193634992, "target": { "key": "f0a1e92df79ac4accab7c34013c52c7539392ed995fa7a0f735d1263a63d6878" } } ], "extra": [ 1, 14, 159, 72, 62, 221, 250, 212, 196, 191, 198, 185, 99, 170, 231, 39, 13, 184, 193, 124, 113, 12, 134, 128, 248, 6, 105, 165, 31, 122, 209, 175, 85, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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