Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef50f3b0ae4571e8cd740cfd8e4bcebe225b066951fb6de088697feb164639c4

Tx prefix hash: 037c0f413f9aa8d30f839cb550d8f189e9b768f5b9566a080a427be18038138e
Tx public key: 4dc4be71e335dc32de016209ff236e120f10a4859e4a1c77e8a04ce3402e9f45
Timestamp: 1700465851 Timestamp [UCT]: 2023-11-20 07:37:31 Age [y:d:h:m:s]: 01:141:14:27:29
Block: 895607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362378 RingCT/type: yes/0
Extra: 014dc4be71e335dc32de016209ff236e120f10a4859e4a1c77e8a04ce3402e9f45021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.661427450000 dcy

stealth address amount amount idx
00: 104cdcd6c9b0f584a0ba87e97971a88265a4ef71f5ac0e1ece90c0623d464d77 0.661427450000 1351846 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": 895617, "vin": [ { "gen": { "height": 895607 } } ], "vout": [ { "amount": 661427450, "target": { "key": "104cdcd6c9b0f584a0ba87e97971a88265a4ef71f5ac0e1ece90c0623d464d77" } } ], "extra": [ 1, 77, 196, 190, 113, 227, 53, 220, 50, 222, 1, 98, 9, 255, 35, 110, 18, 15, 16, 164, 133, 158, 74, 28, 119, 232, 160, 76, 227, 64, 46, 159, 69, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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