Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a681f1afd40467bd5cd6a43fb05d0f1f4388aed133fbae8132015ccf8eb01027

Tx prefix hash: 1af8fb1eff781f71dc17b078330dd12a93a5cf75d3516cc594943fce221e9e71
Tx public key: c2bd7965a46ec2822886ae94bc269613aff25b44b423eea584f7e86032b8b7e4
Timestamp: 1727511343 Timestamp [UCT]: 2024-09-28 08:15:43 Age [y:d:h:m:s]: 00:117:06:21:40
Block: 1119835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83798 RingCT/type: yes/0
Extra: 01c2bd7965a46ec2822886ae94bc269613aff25b44b423eea584f7e86032b8b7e402110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd97d6d65a9fdfc31527871b78b1abb5de2b75f36abe6770f4a1b0fd632fec9d 0.600000000000 1601538 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": 1119845, "vin": [ { "gen": { "height": 1119835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd97d6d65a9fdfc31527871b78b1abb5de2b75f36abe6770f4a1b0fd632fec9d" } } ], "extra": [ 1, 194, 189, 121, 101, 164, 110, 194, 130, 40, 134, 174, 148, 188, 38, 150, 19, 175, 242, 91, 68, 180, 35, 238, 165, 132, 247, 232, 96, 50, 184, 183, 228, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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