Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd883fa144544c7e1c3905e1202b5784616e8acf507d5404c5983116cadc8f84

Tx prefix hash: 6b459aab04a2eed160b78b1364c24f000518da7d905b0e13b38eb68b72e642a3
Tx public key: ab8ac5e2ac1d5c2c80468a713d37ec31d35d4cff7a71380330ff1efbb96605c6
Timestamp: 1701617399 Timestamp [UCT]: 2023-12-03 15:29:59 Age [y:d:h:m:s]: 01:197:02:41:45
Block: 905151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401962 RingCT/type: yes/0
Extra: 01ab8ac5e2ac1d5c2c80468a713d37ec31d35d4cff7a71380330ff1efbb96605c6021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.614977132000 dcy

stealth address amount amount idx
00: 0016484d27c93179e46cf27f41d53e87c26e97bb8e17c42c1a3bef50307f6eab 0.614977132000 1362022 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": 905161, "vin": [ { "gen": { "height": 905151 } } ], "vout": [ { "amount": 614977132, "target": { "key": "0016484d27c93179e46cf27f41d53e87c26e97bb8e17c42c1a3bef50307f6eab" } } ], "extra": [ 1, 171, 138, 197, 226, 172, 29, 92, 44, 128, 70, 138, 113, 61, 55, 236, 49, 211, 93, 76, 255, 122, 113, 56, 3, 48, 255, 30, 251, 185, 102, 5, 198, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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