Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c3e57add495d059f23a8cc097013535b80513aa4990bc64f17ea208cdea5aa

Tx prefix hash: 461bfd625c55e7e525026403c9c1c82152306667638aaa43fa65a4df0147fda4
Tx public key: 03af79ffd36c37307b5b66070fa9c9525caed14e34d28aa3f6b331dc50a87b6f
Timestamp: 1685473323 Timestamp [UCT]: 2023-05-30 19:02:03 Age [y:d:h:m:s]: 02:186:20:56:39
Block: 771566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653376 RingCT/type: yes/0
Extra: 0103af79ffd36c37307b5b66070fa9c9525caed14e34d28aa3f6b331dc50a87b6f02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.704047597000 dcy

stealth address amount amount idx
00: 1f712a14ee45be1bb76a4c2ced24f6db4945df7d5b7cf632a0ed8fdc8e2d5343 1.704047597000 1220939 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": 771576, "vin": [ { "gen": { "height": 771566 } } ], "vout": [ { "amount": 1704047597, "target": { "key": "1f712a14ee45be1bb76a4c2ced24f6db4945df7d5b7cf632a0ed8fdc8e2d5343" } } ], "extra": [ 1, 3, 175, 121, 255, 211, 108, 55, 48, 123, 91, 102, 7, 15, 169, 201, 82, 92, 174, 209, 78, 52, 210, 138, 163, 246, 179, 49, 220, 80, 168, 123, 111, 2, 17, 0, 0, 0, 1, 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