Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b90a56ca0f498af5a43c7e2739335c26b1659267436ac53c112c4738e6d109

Tx prefix hash: 569844c23fb3433af863d57668c95cd7a01141bdab6e6213f96e5ed4d9eacd04
Tx public key: 860cf2dfe0d6cbe88fa4ac5d21a63f391b1d0ed7a92760ade50f3920aa68f6fb
Timestamp: 1676116090 Timestamp [UCT]: 2023-02-11 11:48:10 Age [y:d:h:m:s]: 02:117:15:32:02
Block: 694628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605721 RingCT/type: yes/0
Extra: 01860cf2dfe0d6cbe88fa4ac5d21a63f391b1d0ed7a92760ade50f3920aa68f6fb0211000000015029cbac000000000000000000

1 output(s) for total of 3.064848442000 dcy

stealth address amount amount idx
00: 4861de29dda195d4e59c8fc0cc0a840aeaa782b709cc6a1308435920d384a049 3.064848442000 1137555 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": 694638, "vin": [ { "gen": { "height": 694628 } } ], "vout": [ { "amount": 3064848442, "target": { "key": "4861de29dda195d4e59c8fc0cc0a840aeaa782b709cc6a1308435920d384a049" } } ], "extra": [ 1, 134, 12, 242, 223, 224, 214, 203, 232, 143, 164, 172, 93, 33, 166, 63, 57, 27, 29, 14, 215, 169, 39, 96, 173, 229, 15, 57, 32, 170, 104, 246, 251, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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