Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd756a9dc4b3b8175d5d09d5cd90bca0edf48f55ea3ae7dc7b8681145851f80

Tx prefix hash: d1a81c660fcb41a7562cf8b8e78e556ad449cb954887f90745938d99e6eab153
Tx public key: cf8bcc78fac6c8c4c2c675571e064d5ecdc073e965712f8a1459aec31dc98417
Timestamp: 1694885160 Timestamp [UCT]: 2023-09-16 17:26:00 Age [y:d:h:m:s]: 01:214:06:54:29
Block: 849526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414236 RingCT/type: yes/0
Extra: 01cf8bcc78fac6c8c4c2c675571e064d5ecdc073e965712f8a1459aec31dc9841702110000000575e3f0e9000000000000000000

1 output(s) for total of 0.940086388000 dcy

stealth address amount amount idx
00: 3e9f4f2ad517c88be5bda81dad79620d772456f90b93d887819a68a7113a4771 0.940086388000 1303194 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": 849536, "vin": [ { "gen": { "height": 849526 } } ], "vout": [ { "amount": 940086388, "target": { "key": "3e9f4f2ad517c88be5bda81dad79620d772456f90b93d887819a68a7113a4771" } } ], "extra": [ 1, 207, 139, 204, 120, 250, 198, 200, 196, 194, 198, 117, 87, 30, 6, 77, 94, 205, 192, 115, 233, 101, 113, 47, 138, 20, 89, 174, 195, 29, 201, 132, 23, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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