Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df567f2f4fe35ac17d84873ce37a65be65f1e26fc1adfb80830d547412b4fb35

Tx prefix hash: 5fcb3f87ae3a53032c3737ba7a8ca2e6dc3146a1400b1526b1fb384d34a570f8
Tx public key: 2ac3b633bbbca7636c7f777e2182a73c49bcd334e23981c29a3afffb72552463
Timestamp: 1705964469 Timestamp [UCT]: 2024-01-22 23:01:09 Age [y:d:h:m:s]: 01:146:10:21:57
Block: 941159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365696 RingCT/type: yes/0
Extra: 012ac3b633bbbca7636c7f777e2182a73c49bcd334e23981c29a3afffb7255246302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c7347fc62eb752a2375a5ae3f88247e1674ccd7f1dd9ec0c4fa4d482b33c7f8 0.600000000000 1399303 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": 941169, "vin": [ { "gen": { "height": 941159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c7347fc62eb752a2375a5ae3f88247e1674ccd7f1dd9ec0c4fa4d482b33c7f8" } } ], "extra": [ 1, 42, 195, 182, 51, 187, 188, 167, 99, 108, 127, 119, 126, 33, 130, 167, 60, 73, 188, 211, 52, 226, 57, 129, 194, 154, 58, 255, 251, 114, 85, 36, 99, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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