Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8cdf94b2d482cf905c5da521dbeb79d51e43bcced66b50d666643534e1a7b23

Tx prefix hash: 4e296830c72119ddb7020556725bb2cd3f733ad8fcd3b7cf5ab13ccb2dedac28
Tx public key: 267cc75bb569a37c0d051f3ab915d082cf61ec68df867dd8c483dd7c2aac997d
Timestamp: 1729094226 Timestamp [UCT]: 2024-10-16 15:57:06 Age [y:d:h:m:s]: 00:149:03:11:00
Block: 1132963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106359 RingCT/type: yes/0
Extra: 01267cc75bb569a37c0d051f3ab915d082cf61ec68df867dd8c483dd7c2aac997d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 766a6bbe2d65ef4b6e73a8f063b41ec6d52868f76a0f6537875b7c5e7b19a8fa 0.600000000000 1616012 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": 1132973, "vin": [ { "gen": { "height": 1132963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "766a6bbe2d65ef4b6e73a8f063b41ec6d52868f76a0f6537875b7c5e7b19a8fa" } } ], "extra": [ 1, 38, 124, 199, 91, 181, 105, 163, 124, 13, 5, 31, 58, 185, 21, 208, 130, 207, 97, 236, 104, 223, 134, 125, 216, 196, 131, 221, 124, 42, 172, 153, 125, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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