Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 369189ff08c42a532983362d7307a77e7139a5c09683076cf961b87384b83ced

Tx prefix hash: 3878ca1114c9b0bd8ac2cffda4497e2361064c1a0635b1031e19db6d01b1be91
Tx public key: 7307fb65b9902758edd8cc98da7e68e5ed50c6ab3dd73f11b7f972b7a4d00196
Timestamp: 1700433118 Timestamp [UCT]: 2023-11-19 22:31:58 Age [y:d:h:m:s]: 01:357:20:13:16
Block: 895339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514647 RingCT/type: yes/0
Extra: 017307fb65b9902758edd8cc98da7e68e5ed50c6ab3dd73f11b7f972b7a4d00196021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.662781245000 dcy

stealth address amount amount idx
00: 9abeb7678959fb01fdcbdf22d484a2667b3e772704df3c43ff8143febcf31307 0.662781245000 1351570 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": 895349, "vin": [ { "gen": { "height": 895339 } } ], "vout": [ { "amount": 662781245, "target": { "key": "9abeb7678959fb01fdcbdf22d484a2667b3e772704df3c43ff8143febcf31307" } } ], "extra": [ 1, 115, 7, 251, 101, 185, 144, 39, 88, 237, 216, 204, 152, 218, 126, 104, 229, 237, 80, 198, 171, 61, 215, 63, 17, 183, 249, 114, 183, 164, 208, 1, 150, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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