Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0157e50984a67046466b00714735f065eb22ec70d0a86e091e8f39d427b43d6d

Tx prefix hash: 11e7ca2361a6f05df855c5b34f0b1b782356fcad5cc9842dc67c100905364868
Tx public key: bf1464c3065adc7adb53f9a31e9678defbdf1fb3cd15ce80ecfce3d12727a54c
Timestamp: 1579353424 Timestamp [UCT]: 2020-01-18 13:17:04 Age [y:d:h:m:s]: 05:291:15:18:21
Block: 48392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1356160 RingCT/type: yes/0
Extra: 01bf1464c3065adc7adb53f9a31e9678defbdf1fb3cd15ce80ecfce3d12727a54c021100000001b221b3d1000000000000000000

1 output(s) for total of 424.292694107000 dcy

stealth address amount amount idx
00: 096a0e6746f5b60976e0b1fe6f7f5ae6cb7098a60f77b37b019e3a29214020c9 424.292694107000 89583 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": 48402, "vin": [ { "gen": { "height": 48392 } } ], "vout": [ { "amount": 424292694107, "target": { "key": "096a0e6746f5b60976e0b1fe6f7f5ae6cb7098a60f77b37b019e3a29214020c9" } } ], "extra": [ 1, 191, 20, 100, 195, 6, 90, 220, 122, 219, 83, 249, 163, 30, 150, 120, 222, 251, 223, 31, 179, 205, 21, 206, 128, 236, 252, 227, 209, 39, 39, 165, 76, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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