Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7688960cb10f36195f4ea5405537a109b37f196133aba2b46d2b62614683c97e

Tx prefix hash: 6f62c4b6875f4cf0dea3b40f96142d8a55660e748bd3c1b1c90bed998875b01c
Tx public key: 9cc68213cdbd9defda8a071f4e2056db988c9cc2fdad79c284dcd6a871e1af95
Timestamp: 1703682290 Timestamp [UCT]: 2023-12-27 13:04:50 Age [y:d:h:m:s]: 01:098:11:46:33
Block: 922279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331500 RingCT/type: yes/0
Extra: 019cc68213cdbd9defda8a071f4e2056db988c9cc2fdad79c284dcd6a871e1af95021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9f5e4eb59530af71570e88e1ad66a6ef7f1bdf94cfb8db7cf2410129ed0a6b 0.600000000000 1379975 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": 922289, "vin": [ { "gen": { "height": 922279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9f5e4eb59530af71570e88e1ad66a6ef7f1bdf94cfb8db7cf2410129ed0a6b" } } ], "extra": [ 1, 156, 198, 130, 19, 205, 189, 157, 239, 218, 138, 7, 31, 78, 32, 86, 219, 152, 140, 156, 194, 253, 173, 121, 194, 132, 220, 214, 168, 113, 225, 175, 149, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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