Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a6525b5cd42334d999d8b355dd8fc47a848beb3de02b59b60f3b1ef1f748a1

Tx prefix hash: f126d853f192e819f44c33c9f8d36219f14c10b97cbc593240272542a7709002
Tx public key: 8a57c2caacec5f18bd72d5cdc4ed087099068ca8105aed73418d4c2698f185c0
Timestamp: 1687074439 Timestamp [UCT]: 2023-06-18 07:47:19 Age [y:d:h:m:s]: 01:151:20:56:37
Block: 784840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369900 RingCT/type: yes/0
Extra: 018a57c2caacec5f18bd72d5cdc4ed087099068ca8105aed73418d4c2698f185c002110000000175e3f0e9000000000000000000

1 output(s) for total of 1.539924503000 dcy

stealth address amount amount idx
00: 64f9d261f3f1fc8af221e8dd0464689f14bd94cfaee82bc16c8a183da4a57fc4 1.539924503000 1234741 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": 784850, "vin": [ { "gen": { "height": 784840 } } ], "vout": [ { "amount": 1539924503, "target": { "key": "64f9d261f3f1fc8af221e8dd0464689f14bd94cfaee82bc16c8a183da4a57fc4" } } ], "extra": [ 1, 138, 87, 194, 202, 172, 236, 95, 24, 189, 114, 213, 205, 196, 237, 8, 112, 153, 6, 140, 168, 16, 90, 237, 115, 65, 141, 76, 38, 152, 241, 133, 192, 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