Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 230421c04a1ea9ced16a9d4b89ad4fb66989d33b7bcf963f18df2245f5feac75

Tx prefix hash: 2fab3e4f27d29f56d7630d2bf8a473704942ccc10354337c50eb2a39d5f26e30
Tx public key: e06e858577a333a261835403f1a7109bad53a38a8ed87b08c738f8a472f26c25
Timestamp: 1635624802 Timestamp [UCT]: 2021-10-30 20:13:22 Age [y:d:h:m:s]: 03:135:02:23:21
Block: 363854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 874854 RingCT/type: yes/0
Extra: 01e06e858577a333a261835403f1a7109bad53a38a8ed87b08c738f8a472f26c2502110000000d06faf294000000000000000000

1 output(s) for total of 38.230374817000 dcy

stealth address amount amount idx
00: e9b5f29b9c1707bbc446bff5136d20136ca0a71677ccb7d3df54c22137604cb6 38.230374817000 739376 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": 363864, "vin": [ { "gen": { "height": 363854 } } ], "vout": [ { "amount": 38230374817, "target": { "key": "e9b5f29b9c1707bbc446bff5136d20136ca0a71677ccb7d3df54c22137604cb6" } } ], "extra": [ 1, 224, 110, 133, 133, 119, 163, 51, 162, 97, 131, 84, 3, 241, 167, 16, 155, 173, 83, 163, 138, 142, 216, 123, 8, 199, 56, 248, 164, 114, 242, 108, 37, 2, 17, 0, 0, 0, 13, 6, 250, 242, 148, 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