Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 350f5c40746f278a939465a6b6c2a1b66f82cd116336c96e456ac00209994f78

Tx prefix hash: 853d894eb0e82ea82cbf46b5a9bbc98304d118daab2442cdd429edce784aabe1
Tx public key: 517fd4d7e9f6a44f84531f3f5379842ab00be123582a1c5465af868d6086f463
Timestamp: 1584295131 Timestamp [UCT]: 2020-03-15 17:58:51 Age [y:d:h:m:s]: 05:252:21:12:16
Block: 83403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1334344 RingCT/type: yes/0
Extra: 01517fd4d7e9f6a44f84531f3f5379842ab00be123582a1c5465af868d6086f46302110000000478e4872e000000000000000000

1 output(s) for total of 324.826927146000 dcy

stealth address amount amount idx
00: 1933ed0a02ab0175c6777ff91f7b71eeb6f64e876fcc8b053bdbb8f3fa205ecc 324.826927146000 151661 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": 83413, "vin": [ { "gen": { "height": 83403 } } ], "vout": [ { "amount": 324826927146, "target": { "key": "1933ed0a02ab0175c6777ff91f7b71eeb6f64e876fcc8b053bdbb8f3fa205ecc" } } ], "extra": [ 1, 81, 127, 212, 215, 233, 246, 164, 79, 132, 83, 31, 63, 83, 121, 132, 42, 176, 11, 225, 35, 88, 42, 28, 84, 101, 175, 134, 141, 96, 134, 244, 99, 2, 17, 0, 0, 0, 4, 120, 228, 135, 46, 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