Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5561038aa8d62029ad663e56ec265d653a4175ba2a36faca603130c65903200c

Tx prefix hash: bb2662c56c28048d8db7a9db9730df0aeabb28dab9aee7ebc4e0953bfbba192a
Tx public key: cc696d1fc2b55658fccbd0ed07b42b22a37f7b9f03f47c8203d3e47f0d7ebcd7
Timestamp: 1673654778 Timestamp [UCT]: 2023-01-14 00:06:18 Age [y:d:h:m:s]: 02:000:02:53:52
Block: 674187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521984 RingCT/type: yes/0
Extra: 01cc696d1fc2b55658fccbd0ed07b42b22a37f7b9f03f47c8203d3e47f0d7ebcd7021100000003044c7254000000000000000000

1 output(s) for total of 3.582106978000 dcy

stealth address amount amount idx
00: 7dd1232db9be6e13b4d869056cf255fa72d061b3a7e48b97d16f6fdd55885b61 3.582106978000 1115828 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": 674197, "vin": [ { "gen": { "height": 674187 } } ], "vout": [ { "amount": 3582106978, "target": { "key": "7dd1232db9be6e13b4d869056cf255fa72d061b3a7e48b97d16f6fdd55885b61" } } ], "extra": [ 1, 204, 105, 109, 31, 194, 181, 86, 88, 252, 203, 208, 237, 7, 180, 43, 34, 163, 127, 123, 159, 3, 244, 124, 130, 3, 211, 228, 127, 13, 126, 188, 215, 2, 17, 0, 0, 0, 3, 4, 76, 114, 84, 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