Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 172be9cbfdd2766e17e61982d908bad91843c1e84f09f2404ec17c0b17af577c

Tx prefix hash: b546f931bd5be5cd521edbdbb14aed6507c26c913819d329bc46a7633d272c28
Tx public key: 6cf56ec3aa1d9c5545097d6629a4b92fea416eb8830d39c14f7cbc129e10df30
Timestamp: 1699483158 Timestamp [UCT]: 2023-11-08 22:39:18 Age [y:d:h:m:s]: 01:187:16:25:52
Block: 887465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395365 RingCT/type: yes/0
Extra: 016cf56ec3aa1d9c5545097d6629a4b92fea416eb8830d39c14f7cbc129e10df300211000000014b8f5122000000000000000000

1 output(s) for total of 0.703817486000 dcy

stealth address amount amount idx
00: 3cc6fbd58471af71797800e84a667a8f73eed2d775434e8778b1970fd7161dc5 0.703817486000 1343350 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": 887475, "vin": [ { "gen": { "height": 887465 } } ], "vout": [ { "amount": 703817486, "target": { "key": "3cc6fbd58471af71797800e84a667a8f73eed2d775434e8778b1970fd7161dc5" } } ], "extra": [ 1, 108, 245, 110, 195, 170, 29, 156, 85, 69, 9, 125, 102, 41, 164, 185, 47, 234, 65, 110, 184, 131, 13, 57, 193, 79, 124, 188, 18, 158, 16, 223, 48, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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