Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4289a34698ac1f7be6e038b3d52f5463af3d0ec88b3d307d851a67013a1f4d2

Tx prefix hash: 6b6cc35e9dd2c6454d6dd49d476107575557da8670bd8e34c24078123f951eaa
Tx public key: e5c764640cf244b389e05b1978979648fe5a28807db5acc3f615f278ac4d3ee4
Timestamp: 1583532769 Timestamp [UCT]: 2020-03-06 22:12:49 Age [y:d:h:m:s]: 04:297:20:04:41
Block: 77733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107445 RingCT/type: yes/0
Extra: 01e5c764640cf244b389e05b1978979648fe5a28807db5acc3f615f278ac4d3ee402110000001b4ac5aa02000000000000000000

1 output(s) for total of 339.186919588000 dcy

stealth address amount amount idx
00: e2f6e82e91ecc7512f2c92874f87d7013f31eb447029e761e3ee359a104f9888 339.186919588000 142914 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": 77743, "vin": [ { "gen": { "height": 77733 } } ], "vout": [ { "amount": 339186919588, "target": { "key": "e2f6e82e91ecc7512f2c92874f87d7013f31eb447029e761e3ee359a104f9888" } } ], "extra": [ 1, 229, 199, 100, 100, 12, 242, 68, 179, 137, 224, 91, 25, 120, 151, 150, 72, 254, 90, 40, 128, 125, 181, 172, 195, 246, 21, 242, 120, 172, 77, 62, 228, 2, 17, 0, 0, 0, 27, 74, 197, 170, 2, 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