Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f53563d5628a8b7be3989cbc056e3f2998fcc1adb1ce6f78474297c871cc10e3

Tx prefix hash: 237a8821775ebb3da6191c610e9db4c9c67d0c9e88d0356ec54a65dba4c8fbbe
Tx public key: 53052d6166e52ad89dfcfd6bd29862cef2383790a08443c1dd8f1b29e0b217c0
Timestamp: 1703787165 Timestamp [UCT]: 2023-12-28 18:12:45 Age [y:d:h:m:s]: 01:173:11:00:41
Block: 923145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384987 RingCT/type: yes/0
Extra: 0153052d6166e52ad89dfcfd6bd29862cef2383790a08443c1dd8f1b29e0b217c002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1f31d3b1aaf857ced3de939dbf98e0af904d2cd0e33ec123faad95479d10615 0.600000000000 1380871 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": 923155, "vin": [ { "gen": { "height": 923145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1f31d3b1aaf857ced3de939dbf98e0af904d2cd0e33ec123faad95479d10615" } } ], "extra": [ 1, 83, 5, 45, 97, 102, 229, 42, 216, 157, 252, 253, 107, 210, 152, 98, 206, 242, 56, 55, 144, 160, 132, 67, 193, 221, 143, 27, 41, 224, 178, 23, 192, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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