Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b56104e147064a47492b92bc968b6fe6cef0e5d4885af2d75af85b11126d44d

Tx prefix hash: fc6edae6e40a3e5b17d396405d9fb13dfd4ffa3bda51d9d2b54aeb75d7d79545
Tx public key: 82a2311d32a3e81bc925db8697568f837f5c91d33271d2091199f836ca3e4df2
Timestamp: 1711204277 Timestamp [UCT]: 2024-03-23 14:31:17 Age [y:d:h:m:s]: 01:051:09:39:54
Block: 984659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297712 RingCT/type: yes/0
Extra: 0182a2311d32a3e81bc925db8697568f837f5c91d33271d2091199f836ca3e4df202110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 703ba2bf8e738918ba1b995a91355c5e301a9d41bbb9f9ee2edd656106482d2b 0.600000000000 1444832 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": 984669, "vin": [ { "gen": { "height": 984659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "703ba2bf8e738918ba1b995a91355c5e301a9d41bbb9f9ee2edd656106482d2b" } } ], "extra": [ 1, 130, 162, 49, 29, 50, 163, 232, 27, 201, 37, 219, 134, 151, 86, 143, 131, 127, 92, 145, 211, 50, 113, 210, 9, 17, 153, 248, 54, 202, 62, 77, 242, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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