Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42a8a4f37bae07b1267af28d54d27dcdc8d21306134ebf0d8e8eb2afda67a139

Tx prefix hash: dc2d9f2776f2d74f47e025c0f7bd4def54ef5acced1c1563b90351d02dd951c6
Tx public key: e59284c426f4a84d4c61751576eb08361f0eef024381f01da2ad9e034617d375
Timestamp: 1738826758 Timestamp [UCT]: 2025-02-06 07:25:58 Age [y:d:h:m:s]: 00:355:05:23:53
Block: 1213198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251556 RingCT/type: yes/0
Extra: 01e59284c426f4a84d4c61751576eb08361f0eef024381f01da2ad9e034617d375021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ae792da5a6948bf3ebf6c17abeea6783d6ce9aa986ed7cac73b4f402b4cbb5 0.600000000000 1699975 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": 1213208, "vin": [ { "gen": { "height": 1213198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ae792da5a6948bf3ebf6c17abeea6783d6ce9aa986ed7cac73b4f402b4cbb5" } } ], "extra": [ 1, 229, 146, 132, 196, 38, 244, 168, 77, 76, 97, 117, 21, 118, 235, 8, 54, 31, 14, 239, 2, 67, 129, 240, 29, 162, 173, 158, 3, 70, 23, 211, 117, 2, 17, 0, 0, 0, 5, 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