Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23a7cf9b9529c0b423d3849d281b63e14313f9bc074c4408d06a7245c6f11a3

Tx prefix hash: fb7235a991a5c87ce6771876b3ad6aaa1b0638df3179360121a7781b4db827e8
Tx public key: 46ae3f3557a4ab0d263c24db2eb3ecd85607b80eb549fb486878a74d55e5ac94
Timestamp: 1715434187 Timestamp [UCT]: 2024-05-11 13:29:47 Age [y:d:h:m:s]: 00:335:06:09:43
Block: 1019727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239622 RingCT/type: yes/0
Extra: 0146ae3f3557a4ab0d263c24db2eb3ecd85607b80eb549fb486878a74d55e5ac94021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769d521de180783d1d7b3690cef2ed5d258408e8eb08b4e95af92a3f0ad80285 0.600000000000 1483768 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": 1019737, "vin": [ { "gen": { "height": 1019727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769d521de180783d1d7b3690cef2ed5d258408e8eb08b4e95af92a3f0ad80285" } } ], "extra": [ 1, 70, 174, 63, 53, 87, 164, 171, 13, 38, 60, 36, 219, 46, 179, 236, 216, 86, 7, 184, 14, 181, 73, 251, 72, 104, 120, 167, 77, 85, 229, 172, 148, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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