Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e688ecdaa7a1e896d68eb67c7efbfc3ea4df5872aee59a94d335de0cfb88f72

Tx prefix hash: c7ee3acb51480e34c21cbfcdbcaff26a3525ce74f793370a597956fe5b1650e0
Tx public key: a7a45e7ee986916ec436927056f887a36ef8f11df850809d13029c5005ef13f5
Timestamp: 1682954899 Timestamp [UCT]: 2023-05-01 15:28:19 Age [y:d:h:m:s]: 01:346:16:32:37
Block: 750681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509034 RingCT/type: yes/0
Extra: 01a7a45e7ee986916ec436927056f887a36ef8f11df850809d13029c5005ef13f5021100000003b3164c24000000000000000000

1 output(s) for total of 1.998400026000 dcy

stealth address amount amount idx
00: 3d052c3c308c09ee287e218ea2fec574b40aa127d97a3b7f6abe78b34f8468d1 1.998400026000 1198774 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": 750691, "vin": [ { "gen": { "height": 750681 } } ], "vout": [ { "amount": 1998400026, "target": { "key": "3d052c3c308c09ee287e218ea2fec574b40aa127d97a3b7f6abe78b34f8468d1" } } ], "extra": [ 1, 167, 164, 94, 126, 233, 134, 145, 110, 196, 54, 146, 112, 86, 248, 135, 163, 110, 248, 241, 29, 248, 80, 128, 157, 19, 2, 156, 80, 5, 239, 19, 245, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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