Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d618ee2dafeb2d47d149eb985e4621e1b6d4b1bde456b63c1108c580de147af2

Tx prefix hash: 2b141b44a3873cdd1e2fa225fe9d48b6d124af8c0c1436292f79a9a93e4ad726
Tx public key: a357dda4779d78ab6b120de56244e8285aa7c36c8c2504296f672643bc936d0d
Timestamp: 1732257807 Timestamp [UCT]: 2024-11-22 06:43:27 Age [y:d:h:m:s]: 00:132:01:20:12
Block: 1159079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94192 RingCT/type: yes/0
Extra: 01a357dda4779d78ab6b120de56244e8285aa7c36c8c2504296f672643bc936d0d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 340b3b247df53ca5a8e51b8b91b5d6bd061d491e4f08e3407307e0d31ca31d14 0.600000000000 1644710 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": 1159089, "vin": [ { "gen": { "height": 1159079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "340b3b247df53ca5a8e51b8b91b5d6bd061d491e4f08e3407307e0d31ca31d14" } } ], "extra": [ 1, 163, 87, 221, 164, 119, 157, 120, 171, 107, 18, 13, 229, 98, 68, 232, 40, 90, 167, 195, 108, 140, 37, 4, 41, 111, 103, 38, 67, 188, 147, 109, 13, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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