Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c41e9274f0e36ea7b547af2db9930beae731cb8c1dc3190500f0c40cd23c0076

Tx prefix hash: c27ecda562df0dc94466caf4876c6a716c4f9e6af16ed553686ba6ac96c4cdf3
Tx public key: 6eeedc52f5f96a0ff3ee792cbc5aeb526db60c88a347f6914e21df783b71d88b
Timestamp: 1695980319 Timestamp [UCT]: 2023-09-29 09:38:39 Age [y:d:h:m:s]: 01:188:07:34:09
Block: 858627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395637 RingCT/type: yes/0
Extra: 016eeedc52f5f96a0ff3ee792cbc5aeb526db60c88a347f6914e21df783b71d88b021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.877025781000 dcy

stealth address amount amount idx
00: e6ca5ec625dad5a5efb5425c4e726ea8bd6496a45a8f671fec7968d33670f6e0 0.877025781000 1312811 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": 858637, "vin": [ { "gen": { "height": 858627 } } ], "vout": [ { "amount": 877025781, "target": { "key": "e6ca5ec625dad5a5efb5425c4e726ea8bd6496a45a8f671fec7968d33670f6e0" } } ], "extra": [ 1, 110, 238, 220, 82, 245, 249, 106, 15, 243, 238, 121, 44, 188, 90, 235, 82, 109, 182, 12, 136, 163, 71, 246, 145, 78, 33, 223, 120, 59, 113, 216, 139, 2, 17, 0, 0, 0, 5, 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