Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abb9539e2ea5bdee08e13765386d0ff82c82e0d269fac502cc2c5f1564e10c91

Tx prefix hash: 553d26bcc2d6162f14941934f14f69f98296d72df1c9821a14d8dd2764f02954
Tx public key: ff487567f521062cdf80958880f5987b6e55a874e5dd825af6c7ce375cf73ea2
Timestamp: 1697401281 Timestamp [UCT]: 2023-10-15 20:21:21 Age [y:d:h:m:s]: 01:182:02:18:53
Block: 870404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391166 RingCT/type: yes/0
Extra: 01ff487567f521062cdf80958880f5987b6e55a874e5dd825af6c7ce375cf73ea202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.801660071000 dcy

stealth address amount amount idx
00: 2acf555c4850e882d4dce587d75a4982122c61ca672faac6eaf8147ca177778f 0.801660071000 1325283 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": 870414, "vin": [ { "gen": { "height": 870404 } } ], "vout": [ { "amount": 801660071, "target": { "key": "2acf555c4850e882d4dce587d75a4982122c61ca672faac6eaf8147ca177778f" } } ], "extra": [ 1, 255, 72, 117, 103, 245, 33, 6, 44, 223, 128, 149, 136, 128, 245, 152, 123, 110, 85, 168, 116, 229, 221, 130, 90, 246, 199, 206, 55, 92, 247, 62, 162, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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