Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271c43e1fa97159be13f07a2f13cb8188b041fe60d35322c5f64f9e3adc5b3e2

Tx prefix hash: 0dab4a7dc6d9a02b96a8fedfc70ac5fc437bedfb26416ebbfa135a4ce7974271
Tx public key: 712277917c5d2b338771dc3f6f3b8d662d66f09d0d819cbf53a4952aac65b2ea
Timestamp: 1715466041 Timestamp [UCT]: 2024-05-11 22:20:41 Age [y:d:h:m:s]: 01:005:05:59:58
Block: 1019993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264647 RingCT/type: yes/0
Extra: 01712277917c5d2b338771dc3f6f3b8d662d66f09d0d819cbf53a4952aac65b2ea021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06639830dd097fb23330036540037ac33f25d47f48a8d4cf5f06aebe1907999 0.600000000000 1484052 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": 1020003, "vin": [ { "gen": { "height": 1019993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06639830dd097fb23330036540037ac33f25d47f48a8d4cf5f06aebe1907999" } } ], "extra": [ 1, 113, 34, 119, 145, 124, 93, 43, 51, 135, 113, 220, 63, 111, 59, 141, 102, 45, 102, 240, 157, 13, 129, 156, 191, 83, 164, 149, 42, 172, 101, 178, 234, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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