Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e162d0f175bd297e187b1f4b92d5246e3d789e9ce6277de096ac3f7eb789c512

Tx prefix hash: 1dd5f4715c3ef68da02a1ca93447a4d6029ca5c1ad0b44b97fbfae14f53d468b
Tx public key: bc9d2e4ec9cd6341f296778f5414bd5bc072f73619198ea238a36884975a9331
Timestamp: 1716510971 Timestamp [UCT]: 2024-05-24 00:36:11 Age [y:d:h:m:s]: 00:244:14:47:48
Block: 1028632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175026 RingCT/type: yes/0
Extra: 01bc9d2e4ec9cd6341f296778f5414bd5bc072f73619198ea238a36884975a933102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8ea81b942aa5d599fd30ca4d15a288ae4342910b164a7d3ca46953236c9c5b7 0.600000000000 1496627 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": 1028642, "vin": [ { "gen": { "height": 1028632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8ea81b942aa5d599fd30ca4d15a288ae4342910b164a7d3ca46953236c9c5b7" } } ], "extra": [ 1, 188, 157, 46, 78, 201, 205, 99, 65, 242, 150, 119, 143, 84, 20, 189, 91, 192, 114, 247, 54, 25, 25, 142, 162, 56, 163, 104, 132, 151, 90, 147, 49, 2, 17, 0, 0, 0, 2, 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