Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5678ff5f44eac60a64c1114a941a93babf8544c2b85f9a0bd0f2b711fa1d44

Tx prefix hash: 3a72603a913157e6a6d648515d215bffac7fead7c30785644459fa8b81d0f64a
Tx public key: 106685f0632dec183d36cc413956e1cc55f423591a2f5e4cc3d3684980c313ff
Timestamp: 1707826364 Timestamp [UCT]: 2024-02-13 12:12:44 Age [y:d:h:m:s]: 01:059:21:11:26
Block: 956631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303838 RingCT/type: yes/0
Extra: 01106685f0632dec183d36cc413956e1cc55f423591a2f5e4cc3d3684980c313ff02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6415ed496f811eee2325c85e65fd3b05dddc0cd81035dcdc9517738fafcc251b 0.600000000000 1415939 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": 956641, "vin": [ { "gen": { "height": 956631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6415ed496f811eee2325c85e65fd3b05dddc0cd81035dcdc9517738fafcc251b" } } ], "extra": [ 1, 16, 102, 133, 240, 99, 45, 236, 24, 61, 54, 204, 65, 57, 86, 225, 204, 85, 244, 35, 89, 26, 47, 94, 76, 195, 211, 104, 73, 128, 195, 19, 255, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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