Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 414b6a7911ba0220b6c99c14b5a2b5f3f7ad663fba896437c535903116fd0dbb

Tx prefix hash: 3328ea9eb660786316b2fc94be5c4c13c73ac44837f379b9f6fbf0fe3b38644a
Tx public key: e832e61f25b8dbe357e9797f58c6b4a70854dbd54c6787fda19250d26d1be058
Timestamp: 1735450405 Timestamp [UCT]: 2024-12-29 05:33:25 Age [y:d:h:m:s]: 00:117:14:01:17
Block: 1185514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83849 RingCT/type: yes/0
Extra: 01e832e61f25b8dbe357e9797f58c6b4a70854dbd54c6787fda19250d26d1be058021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff10e6807127317e469977ffe7ecba72c90877812b31c40c33c8e2fe72f1a57c 0.600000000000 1671987 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": 1185524, "vin": [ { "gen": { "height": 1185514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff10e6807127317e469977ffe7ecba72c90877812b31c40c33c8e2fe72f1a57c" } } ], "extra": [ 1, 232, 50, 230, 31, 37, 184, 219, 227, 87, 233, 121, 127, 88, 198, 180, 167, 8, 84, 219, 213, 76, 103, 135, 253, 161, 146, 80, 210, 109, 27, 224, 88, 2, 17, 0, 0, 0, 4, 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