Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f280e20e38685b6db5952287b4c70b8af6cc339190aff88f474679124485853

Tx prefix hash: a7dc0c1274ecda6248e18a81249701a3cb0f363a9ed70c022b93a975f57eaea5
Tx public key: a04b4f9ee86744fb967f9d6ca48a9cccaeb36c865acf9585d73acd4b3affe4c3
Timestamp: 1704191963 Timestamp [UCT]: 2024-01-02 10:39:23 Age [y:d:h:m:s]: 01:055:23:14:05
Block: 926491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301080 RingCT/type: yes/0
Extra: 01a04b4f9ee86744fb967f9d6ca48a9cccaeb36c865acf9585d73acd4b3affe4c302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf0075e5af33685afe422d2957184369cf95f2a354f68c62d0b497f6fac15d02 0.600000000000 1384277 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": 926501, "vin": [ { "gen": { "height": 926491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf0075e5af33685afe422d2957184369cf95f2a354f68c62d0b497f6fac15d02" } } ], "extra": [ 1, 160, 75, 79, 158, 232, 103, 68, 251, 150, 127, 157, 108, 164, 138, 156, 204, 174, 179, 108, 134, 90, 207, 149, 133, 215, 58, 205, 75, 58, 255, 228, 195, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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