Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e86a35b16768ff8ea90d16ca5886b90e34e18f16ff4b376f700d510619d6e96d

Tx prefix hash: 96628b5d8cdc027351caf2474384f17ebc8370a1be9a4a680734837674c16976
Tx public key: 269013d9dff253b11dad6c58d9783d3b4c8dcfa1bdb9524a46e16be5ffade278
Timestamp: 1705549792 Timestamp [UCT]: 2024-01-18 03:49:52 Age [y:d:h:m:s]: 01:099:06:52:58
Block: 937728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332088 RingCT/type: yes/0
Extra: 01269013d9dff253b11dad6c58d9783d3b4c8dcfa1bdb9524a46e16be5ffade2780211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ef2567e31542f37ab3030336fc0bba71d5e8b6880de1d0ead7a1fd6d5d51aac 0.600000000000 1395790 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": 937738, "vin": [ { "gen": { "height": 937728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ef2567e31542f37ab3030336fc0bba71d5e8b6880de1d0ead7a1fd6d5d51aac" } } ], "extra": [ 1, 38, 144, 19, 217, 223, 242, 83, 177, 29, 173, 108, 88, 217, 120, 61, 59, 76, 141, 207, 161, 189, 185, 82, 74, 70, 225, 107, 229, 255, 173, 226, 120, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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