Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ad470a7c66d60c925d94e962f26fbe89cb8923afcbcada9891fa21e195f1ec

Tx prefix hash: 31d22325a101024cfad983495635c671a8b332059108dbbfb54f43ad82f139b9
Tx public key: c6d3f8a237002092080795e59e8c6f9505a81c0cb25e88465ccc224e181f4996
Timestamp: 1732999688 Timestamp [UCT]: 2024-11-30 20:48:08 Age [y:d:h:m:s]: 00:203:06:07:28
Block: 1165228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144928 RingCT/type: yes/0
Extra: 01c6d3f8a237002092080795e59e8c6f9505a81c0cb25e88465ccc224e181f4996021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3044007ae06aa5db39042bd2441185814679ce9e8400cb5a2617ac4d6acecfdf 0.600000000000 1650903 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": 1165238, "vin": [ { "gen": { "height": 1165228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3044007ae06aa5db39042bd2441185814679ce9e8400cb5a2617ac4d6acecfdf" } } ], "extra": [ 1, 198, 211, 248, 162, 55, 0, 32, 146, 8, 7, 149, 229, 158, 140, 111, 149, 5, 168, 28, 12, 178, 94, 136, 70, 92, 204, 34, 78, 24, 31, 73, 150, 2, 17, 0, 0, 0, 3, 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