Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d26749bbe9ddc59ce5d0caa7e0a32fb5620953087c42a4e55c1953037cf98a80

Tx prefix hash: af9fd775abfc8054a4726731a8a46206a04efc498f7eb9a75111abdaa5cf5d5e
Tx public key: 8df200b3f667301560444a07fdc4e95d3a40f444b0eba8c27c5324e65ccad305
Timestamp: 1681461761 Timestamp [UCT]: 2023-04-14 08:42:41 Age [y:d:h:m:s]: 02:003:20:55:38
Block: 738290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524919 RingCT/type: yes/0
Extra: 018df200b3f667301560444a07fdc4e95d3a40f444b0eba8c27c5324e65ccad30502110000000a5029cbac000000000000000000

1 output(s) for total of 2.196539267000 dcy

stealth address amount amount idx
00: b60b82f9f678a8c3aeaf3a59c4f6911b3691145b0a0d02a4d44ab1619e11c421 2.196539267000 1184965 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": 738300, "vin": [ { "gen": { "height": 738290 } } ], "vout": [ { "amount": 2196539267, "target": { "key": "b60b82f9f678a8c3aeaf3a59c4f6911b3691145b0a0d02a4d44ab1619e11c421" } } ], "extra": [ 1, 141, 242, 0, 179, 246, 103, 48, 21, 96, 68, 74, 7, 253, 196, 233, 93, 58, 64, 244, 68, 176, 235, 168, 194, 124, 83, 36, 230, 92, 202, 211, 5, 2, 17, 0, 0, 0, 10, 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